FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.ehrsfmr21#current (16 ms)

Package hl7.ehrs.ehrsfmr21
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.1.3.html
Url http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.1.3
Version 2.1.0
Status active
Date 2024-11-26T16:30:50+00:00
Name CPS_1_3_Capture_Quick_Registration
Title CPS.1.3 Capture Quick Registration (Function)
Experimental False
Realm uv
Authority hl7
Description Capture a registration, either directly entered or received from an external system, without complete supporting demographics, in order to facilitate patient care before the full registration is complete.
Purpose The registration process, including the verification of full demographics data, insurance, contact information, etc. is frequently time consuming. To facilitate patient care in emergency situations, the system must be able to register a patient with minimal information in a time critical manner. Examples of situations when this might be necessary include when a patient presents with acute myocardial infarction, a disaster response, or a mass casualty event. After care is given during an emergent situation, records are often incomplete or invalid. Such records may need to be completed and validated. Afterwards, those records may need to be harmonized. For example, the records of "John Doe1; approximate age is 30" may need to be matched with existing records for "Henry Smith; age 28".

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Capture a registration, either directly entered or received from an external system, without complete supporting demographics, in order to facilitate patient care before the full registration is complete.

Description I:

The registration process, including the verification of full demographics data, insurance, contact information, etc. is frequently time consuming. To facilitate patient care in emergency situations, the system must be able to register a patient with minimal information in a time critical manner. Examples of situations when this might be necessary include when a patient presents with acute myocardial infarction, a disaster response, or a mass casualty event.

After care is given during an emergent situation, records are often incomplete or invalid. Such records may need to be completed and validated. Afterwards, those records may need to be harmonized. For example, the records of "John Doe1; approximate age is 30" may need to be matched with existing records for "Henry Smith; age 28".

Criteria N:
CPS.1.3#01 SHALL

The system SHALL provide the ability to capture patient registration information to accommodate an expedited registration situation (e.g., during a disaster or during a census overload at a facility).

CPS.1.3#02 SHOULD

The system SHOULD provide the ability to capture registration through integration with an external system (e.g., Hospital ADT) before all identifying data is known.

CPS.1.3#03 SHALL

The system SHALL provide the ability to harmonize information generated during an expedited registration process with the EHR.


Source

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-CPS.1.3",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Capture a registration, either directly entered or received from an external system, without complete supporting demographics, in order to facilitate patient care before the full registration is complete.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The registration process, including the verification of full demographics data, insurance, contact information, etc. is frequently time consuming. To facilitate patient care in emergency situations, the system must be able to register a patient with minimal information in a time critical manner. Examples of situations when this might be necessary include when a patient presents with acute myocardial infarction, a disaster response, or a mass casualty event.</p>\n<p>After care is given during an emergent situation, records are often incomplete or invalid. Such records may need to be completed and validated. Afterwards, those records may need to be harmonized. For example, the records of &quot;John Doe1; approximate age is 30&quot; may need to be matched with existing records for &quot;Henry Smith; age 28&quot;.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.1.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture patient registration information to accommodate an expedited registration situation (e.g., during a disaster or during a census overload at a facility).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.1.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture registration through integration with an external system (e.g., Hospital ADT) before all identifying data is known.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.1.3#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to harmonize information generated during an expedited registration process with the EHR.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.1.3",
  "version" : "2.1.0",
  "name" : "CPS_1_3_Capture_Quick_Registration",
  "title" : "CPS.1.3 Capture Quick Registration (Function)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Capture a registration, either directly entered or received from an external system, without complete supporting demographics, in order to facilitate patient care before the full registration is complete.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "The registration process, including the verification of full demographics data, insurance, contact information, etc. is frequently time consuming. To facilitate patient care in emergency situations, the system must be able to register a patient with minimal information in a time critical manner. Examples of situations when this might be necessary include when a patient presents with acute myocardial infarction, a disaster response, or a mass casualty event.\n\nAfter care is given during an emergent situation, records are often incomplete or invalid. Such records may need to be completed and validated. Afterwards, those records may need to be harmonized. For example, the records of \"John Doe1; approximate age is 30\" may need to be matched with existing records for \"Henry Smith; age 28\".",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CPS.1.3-01",
      "label" : "CPS.1.3#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to capture patient registration information to accommodate an expedited registration situation (e.g., during a disaster or during a census overload at a facility)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CPS.1.3-02",
      "label" : "CPS.1.3#02",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to capture registration through integration with an external system (e.g., Hospital ADT) before all identifying data is known."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CPS.1.3-03",
      "label" : "CPS.1.3#03",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to harmonize information generated during an expedited registration process with the EHR."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.